treewide: Enforce C17 as the minimum required C standard #97076
Conversation
zephyrbot
added
area: Kconfig
area: Toolchains
zephyrbot
requested review from
57300,
jeremybettis,
nashif,
nordicjm,
stephanosio,
tejlmand and
yonsch
|
@stephanosio @nashif @keith-packard should we also enforce C++17 at the same time, for consistency? |
C99 has been the minimum required C standard version for Zephyr since its inception. After multiple attempts and discussions, a decision has been made to upgrade to C17 going forward. This commits replaces the default C standard from C99 to C17 in the configuration and build system. Signed-off-by: Carles Cufi <[email protected]>
As part of the transition from C99 to C17 as the minimum supported C standard version, remove the workarounds in the formatted output subsystem to maintain compatibility with toolchains that do not support the _Generic keyword. Signed-off-by: Carles Cufi <[email protected]>
|
There was a problem hiding this comment.
Do we need to drop these compiler feature flags? This will require all out-of-tree dependencies to drop this (even if they do support an older C standard version?).
I think this can remain, as newer standards should support older flags.
|
@nashif You may want to consider switching to MISRA C:2012 Amendment 3 as a basis for the guidelines after updating the baseline C standard version, since that edition of the guidelines have much better coverage of C17 than Amendment 2 (e.g. it has guidelines for the safe use of |
C99 has been the minimum required C standard version for Zephyr since its inception. After multiple attempts and discussions, a decision has been made to upgrade to C17 going forward.
This commits replaces the default C standard from C99 to C17 in the configuration and build system.